Changes to the affiliation policy#1921
Conversation
✅ Deploy Preview for earnest-hotteok-b1e1bf ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hello @caterina-doglioni, and thank you very much! I see that you did not work atop my other PR #1918 on the updates to the affiliation programme. I will see if I can rebase/"merge" but otherwise we can review and in the end merge together. Agreed that we can leave the PRs open since it is easy enough to use the preview to check the new version, when diffs are non-obvious sometimes. |
|
|
||
| EVERSE is a EU-funded project (GA 101129744, HORIZON-INFRA-2023-EOSC-01-02) aiming to create a framework for research software and code excellence, collaboratively designed and championed by the research communities, in pursuit of building a European network of Research Software Quality and setting the foundations of a future Virtual Institute for Research Software Excellence. | ||
|
|
||
| EVERSE has the following objectives: |
There was a problem hiding this comment.
Just in case, is there an EVERSE document one can refer to here or at the bottom of this list/section for a comprehensive description? Guess so, and probably a good thing to provide the pointer.
Co-authored-by: Eduardo Rodrigues <eduardo.rodrigues@cern.ch>
Co-authored-by: Eduardo Rodrigues <eduardo.rodrigues@cern.ch>
Co-authored-by: Eduardo Rodrigues <eduardo.rodrigues@cern.ch>
|
Good morning @caterina-doglioni, I went ahead and committed my suggestions since nobody complained in several days :). |
|
Great, thanks! I should have 1h or so this afternoon to get your changes in as well (unless you've done that already, haven't checked :) ) |
| From these levels we have developed guidelines that projects can examine to | ||
| understand typical levels of maturity, developer support, community support and | ||
| engagement. | ||
| **Research software infrastructure** include software that captures broadly accepted ideas, methods and models for use in research, often warranting close involvement of researchers in its development. This kind of software is broadly applicable, but it does not necessarily mean that its codebase will be large. A research software classed as infrastructure could be a comprehensive toolkit meeting a research need, but it could also be a smaller focused software package that is essential for several research communities. In the case of research software infrastructure, the maturity of the codebase, developer support, community support and engagement warrant specific recommendations. |
There was a problem hiding this comment.
| **Research software infrastructure** include software that captures broadly accepted ideas, methods and models for use in research, often warranting close involvement of researchers in its development. This kind of software is broadly applicable, but it does not necessarily mean that its codebase will be large. A research software classed as infrastructure could be a comprehensive toolkit meeting a research need, but it could also be a smaller focused software package that is essential for several research communities. In the case of research software infrastructure, the maturity of the codebase, developer support, community support and engagement warrant specific recommendations. | |
| **Research software infrastructure** includes software that captures broadly accepted ideas, methods and models for use in research, often warranting close involvement of researchers in its development. This kind of software is broadly applicable, but it does not necessarily mean that its codebase will be large. A research software classed as infrastructure could be a comprehensive toolkit meeting a research need, but it could also be a smaller focused software package that is essential for several research communities. In the case of research software infrastructure, the maturity of the codebase, developer support, community support and engagement warrant specific recommendations. |
eduardo-rodrigues
left a comment
eduardo-rodrigues
left a comment
There was a problem hiding this comment.
Thank you again very much for this important and great update!
|
Hello @caterina-doglioni, indeed I went ahead and implemented my little suggestions, and merged. They were basically additions of links. See if OK with you. Otherwise there are 2 trivial things, up to you. In any case, as per the SG discussions, this important update is now approved. Merge when done/happy. Thank you to everyone who contributed! |
3 participants
This PR adds changes to the projects and affiliation pages that were mentioned in an email to the SG, namely:
I'd be very happy to have comments on the wording and text, we can also discuss this at the next SG before merging.
Tagging @roiser @graeme-a-stewart @eduardo-rodrigues for a read and a review.